implement filter-general function #44

janiceelamm · 2025-11-21T19:39:12Z

implement this function that filters volunteers by general information (e.g. email, phone, position,etc.)

Basic testing
test case 1: AND with one unique value (op = "AND", column = "email", values = "v1@mail.com")

test case 2: AND with two values. (op = "AND", column = "pronouns", values = "He/him", "She/her")

Should return empty rows since this is filtering one column only.

test case 3: OR with two values ((op = "AND", column = "pronouns", values = "He/him", "She/her")

test case 4: Invalid op ((op = "hello", column = "email", values = "v1@mail.com")

vercel · 2025-11-21T19:39:19Z

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
trcc	Ready	Preview	Comment	Nov 21, 2025 7:39pm

Copilot

Pull request overview

This PR implements a new filtering API endpoint that allows querying the Volunteers table with AND/OR operations on specific columns. The implementation includes both the core filtering logic and an HTTP route handler to expose this functionality.

Adds a filter_general function with column validation and support for AND/OR operations
Creates a GET endpoint at /api/filter-general to expose the filtering functionality
Implements validation for parameters and returns appropriate error responses

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 7 comments.

File	Description
src/lib/api/filter_general.ts	Core filtering logic with column whitelisting, AND/OR operation support, and Supabase query execution
src/app/api/filter-general/route.ts	HTTP route handler that validates query parameters and calls the filter_general function

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copilot · 2025-11-21T19:42:07Z

src/lib/api/filter_general.ts

+
+  const client = await createClient();
+
+  if (values.length == 0) {


Use strict equality operator (===) instead of loose equality (==) to avoid type coercion issues.

Suggested change

if (values.length == 0) {

if (values.length === 0) {

Copilot · 2025-11-21T19:42:07Z

src/lib/api/filter_general.ts

+    return { data: null, error: "No values provided." };
+  }
+
+  if (op == "AND") {


Use strict equality operator (===) instead of loose equality (==) to avoid type coercion issues.

Copilot · 2025-11-21T19:42:07Z

src/lib/api/filter_general.ts

+    const result = await client.from("Volunteers").select().eq(column, value);
+    return result;
+  }
+  if (op == "OR") {


Use strict equality operator (===) instead of loose equality (==) to avoid type coercion issues.

Suggested change

if (op == "OR") {

if (op === "OR") {

Copilot · 2025-11-21T19:42:07Z

src/lib/api/filter_general.ts

+  if (values.length == 0) {
+    return { data: null, error: "No values provided." };
+  }


The values.length check at line 24 is redundant since the route handler already validates this condition at line 10. This duplicate validation should be removed or the route handler's check should be removed to avoid redundancy.

Suggested change

if (values.length == 0) {

return { data: null, error: "No values provided." };

}

Copilot · 2025-11-21T19:42:08Z

src/lib/api/filter_general.ts

+export async function filter_general(
+  op: string,
+  column: string,
+  values: string[]
+) {


Missing JSDoc documentation for this public API function. Should include descriptions of parameters (op, column, values), the return type, and examples of valid operations. See getExample.ts comments for reference style.

Copilot · 2025-11-21T19:42:08Z

src/lib/api/filter_general.ts

+import { createClient } from "../client/supabase/server";
+
+export async function filter_general(
+  op: string,


The 'op' parameter allows any string value but only 'AND' and 'OR' are valid. Consider using a union type (op: 'AND' | 'OR') to enforce valid values at compile time and improve type safety.

Suggested change

op: string,

op: 'AND' | 'OR',

Copilot · 2025-11-21T19:42:08Z

src/app/api/filter-general/route.ts

+  const column = searchParams.get("column");
+  const values = searchParams.getAll("values");
+
+  if (!op || !column || values.length == 0) {


Use strict equality operator (===) instead of loose equality (==) to avoid type coercion issues.

Suggested change

if (!op || !column || values.length == 0) {

if (!op || !column || values.length === 0) {

ch-iv

We should generally aim to have written tests for every PR. Could you write some tests for the changes you've made?

ch-iv · 2025-11-22T01:44:57Z

src/app/api/filter-general/route.ts

I think the name of the directory filter-general is too generic. We want to convey more information about what this route does by giving it a more descriptive name.

ch-iv · 2025-11-22T01:45:46Z

src/app/api/filter-general/route.ts

We don't need to implement the route.

ch-iv · 2025-11-22T01:46:57Z

src/lib/api/filter_general.ts

@@ -0,0 +1,45 @@
+import { createClient } from "../client/supabase/server";
+
+export async function filter_general(


Similar comment to route naming. This function should be given a more descriptive name. The current name doesn't communicate what this method does.

ch-iv · 2025-11-22T01:47:18Z

src/lib/api/filter_general.ts

+  op: string,
+  column: string,
+  values: string[]
+) {


The return value of this function should be typed.

ch-iv · 2025-11-22T01:50:07Z

src/lib/api/filter_general.ts

+import { createClient } from "../client/supabase/server";
+
+export async function filter_general(
+  op: string,


(nit) Not a big fan of the name op. Something like matchType is more descriptive.

ch-iv · 2025-11-22T01:55:49Z

src/lib/api/filter_general.ts

+import { createClient } from "../client/supabase/server";
+
+export async function filter_general(
+  op: string,


We should rely on the TypeScript type system to enforce the validity of the value of op (as well as for other arguments.)

I suggest you created either an Enum or a literal value type for op.

type MatchType = "any" | "all";

then you can type the function argument as follows:

function filter_general(op: MatchType, ...)

and the ts compiler will let you know if the function contract is being violated when you pass in the wrong values for op.

ch-iv · 2025-11-22T01:56:13Z

src/lib/api/filter_general.ts

+
+export async function filter_general(
+  op: string,
+  column: string,


Same comment as for OP. This should be a type or an enum.

ch-iv · 2025-11-22T01:57:08Z

src/lib/api/filter_general.ts

+  const valid_columns = [
+    "name_org",
+    "pseudonym",
+    "pronouns",
+    "email",
+    "phone",
+    "position",
+    "opt_in_communication",
+  ];


We should get rid of this in favor of introducing a type or an enum for valid columns in a centralized helper in this codebase.

ch-iv · 2025-11-22T02:15:36Z

src/lib/api/filter_general.ts

+    return { data: null, error: "Invalid column name" };
+  }
+
+  const client = await createClient();


This should be moved to be after all of the validation checks. This way we don't have to create a client before returning due to values being empty.

implement filter-general function

f03ef87

Copilot AI review requested due to automatic review settings November 21, 2025 19:39

Copilot started reviewing on behalf of janiceelamm November 21, 2025 19:39 View session

vercel bot deployed to Preview November 21, 2025 19:39 View deployment

Copilot finished reviewing on behalf of janiceelamm November 21, 2025 19:41

Copilot AI reviewed Nov 21, 2025

View reviewed changes

ch-iv requested changes Nov 22, 2025

View reviewed changes


		const client = await createClient();

		if (values.length == 0) {

	if (values.length == 0) {
	return { data: null, error: "No values provided." };
	}

	if (!op \|\| !column \|\| values.length == 0) {
	if (!op \|\| !column \|\| values.length === 0) {

		@@ -0,0 +1,45 @@
		import { createClient } from "../client/supabase/server";

		export async function filter_general(

implement filter-general function #44

Are you sure you want to change the base?

implement filter-general function #44

Uh oh!

Conversation

janiceelamm commented Nov 21, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

vercel bot commented Nov 21, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Copilot AI Nov 21, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Nov 21, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Nov 21, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Nov 21, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Nov 21, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Nov 21, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Nov 21, 2025

Choose a reason for hiding this comment

Uh oh!

ch-iv left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

janiceelamm commented Nov 21, 2025 •

edited

Loading

vercel bot commented Nov 21, 2025 •

edited

Loading